Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1073

reference
838-tree-1
name
1073
tree-preservation-order

undefined

838-tpo-1
uprn
address-text
point
POINT (-1.046360 50.858078)
geometry
MULTIPOLYGON (((-1.046275 50.858069,-1.046279 50.858085,-1.046291 50.858101,-1.046310 50.858113,-1.046333 50.858120,-1.046359 50.858123,-1.046386 50.858121,-1.046410 50.858113,-1.046429 50.858102,-1.046441 50.858087,-1.046446 50.858070,-1.046442 50.858053,-1.046430 50.858038,-1.046412 50.858026,-1.046388 50.858018,-1.046362 50.858015,-1.046335 50.858018,-1.046311 50.858025,-1.046292 50.858037,-1.046280 50.858052,-1.046275 50.858069)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL